6.2.0 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
- Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-8: Runtime Subroutine's and Predefined Processes

.UTIL.KILL.SESSION


This subroutine Cancels the specified process.

Usage:

Description:

This subroutine will attempt to cancel (kill) the specified process. The <PID> parameter is required, if it is missing, the subroutine will CANCEL.

<PID> is the process id you want to cancel, in decimal format.

<Error Message> is an optional parameter that will contain more information if the process could not be cancelled. This must be PASSed with the Share flag to return a result.

If the current user is an APPX System Administrator, then any valid <PID> is allowed (including non APPX processes). If the current user is not an APPX administrator they can only cancel one of their own APPX processes.

The restrictions applied by the host operating system still apply, i.e., if the current user is not an Administrator at the O/S level they will probably not be allowed to cancel other user's processes even if they are an APPX System Administrator.

Application Design Manual                                         "Powered by Appx Software"

1592

©2006-2023 By APPX Software, Inc. All Rights Reserved